Instant video- and voicemail messaging method and means

ABSTRACT

The invention relates to the field of instant messaging. More specifically the invention relates to a server centric method and unit for instant voice and video mail messaging. Even more particularly the invention relates to voicemail messaging with mobile terminals. The inventive methods and units under study allow faster voice messaging and enable similar, but not identical audio/video message “ping ball”. The sending of voicemail in accordance with the invention is instantaneous and involves no different telephone numbers for the sender to remember. The reception of messages is always instantaneous, provided the recipient is available, and only if not available, may the delivery of the messages be delayed.

PRIORITY REQUEST DATA

A previous patent application describes an invention with same goals andessence in patent application FI20001838 with server independentembodiments, where servers are used only as a backup, which is heretaken as reference and priority of which is requested.

FIELD OF INVENTION

The invention relates to the field of instant messaging. Morespecifically the invention relates to a server centric method and meansfor instant voice and video mail messaging. Even more particularly theinvention relates voicemail messaging with mobile terminals.

BACKGROUND

For further prior art to this invention, we wish to submit WO 01/54387A1, Nguyen. This document discloses a method where: “A unique telephonenumber and extension are associated with each (1) one of a plurality ofsubscribers (105). The telephone number is also associated with a remoteaccess point of presence (RAPP) (120). Messages are left for subscribersby establishing a phone call to the phone number associated therewith.The phone call is received at a RAPP (120). The RAPP (120) receives thevoice message, digitises and pocketsize the voice message, and transmitsthe message over a packet network (130) to a store and forward messagingsystem (125). The store and forward messaging system stores the messagefor retrieval. The message can be retrieved by either telephone, aclient computer, or a private branch exchange terminal (110).” Thisdocument is cited here as reference.

In addition prior art methods in delivering messages include Cellularvoicemail and SMS (Short Message Service) messages. SMS messages aretext-based messages, which are delivered to the terminal directly as afirst priority, and stored on the network if delivery is unavailable.With Cellular Voicemail it is possible to call the voicemail box of therecipient, and the recipient of the voicemail may later listen themessage.

This prior art has several disadvantages in contrast with the inventionin the priority document and this inventive method under study based onthe priority document. SMS messages are restricted to text which isharder to input than voice by speech. SMS messages are therefore tediousto the sender. Cellular voicemail is both tedious to send and receive.In order to send voicemail, the sender has to know the telephone numberof the voicemail box of the recipient, which is typically different fromthe phone number, or wait for the voicemail box to connect to theoriginal telephone number when the recipient is not available. In orderto receive voicemail, the recipient needs to retrieve the message fromthe network, because the message is not delivered instantly to him.

SUMMARY

The method under study is far faster and enables similar, but notidentical audio/video message “ping ball” as described in the prioritydocument. The sending of voicemail in accordance with the invention isinstantaneous and involves no different telephone numbers for the senderto remember. The reception of messages is always instantaneous, providedthe recipient is available, and only if not available, may the deliveryof the messages be delayed.

The aforementioned advantages are best realised with an exemplaryembodiment of the invention, in which the user has a softwareapplication running on his subscriber terminal. The user chooses arecipient for a voice- or video mail from the contacts book of theterminal by pressing a button. The terminal forms a data connection to aserver or dials a telephone connection to a server, which typically hasa low latency i.e. the connection to the server is formed fast. Thesubscriber terminal sends the contact information of the recipient tothe server. The subscriber terminal, the server or both indicate to theuser that the recording of the message is begun or may be started. Therecording is displayed and/or dictated down to phone line to the serveror through a packet switched connection to the server. The server storesthe recording typically in MP3-, WAV- or RealSystem Secure, u-law,A-law, PCM or ADPCM or the like format to a database. There is typicallya DSP circuit that digitises the recording to a data file. Alternativelytape recording may be used. The server inspects the phone number, IPaddress or other contact directory of the recipient, and routes themessage file, or a copy of it, to a server in close proximity in theSFSN (Store and Forward Server Network). This server, or alternativelythe original server, then establishes a communication connection to therecipient(s). The connection is typically established by a phone call tothe recipient, and when the recipient answers the message is played tothe recipient. Prefixes and postfixes may be attached to the messagesuch as: “Message of Ms. Vilma Väänänen” MESSAGE “The message of VilmaVäänänen was brought to you by OPERATOR.”

A video and/or voicemail messaging method, comprising at least onesubscriber terminal and at least one server, in accordance with theinvention is characterised by the steps of,

-   -   choosing at least one message recipient or a group,    -   forming a communications connection to at least one server,    -   recording at least one voice/video message to at least one        server via at least one established communications connection,    -   transferring at least one contact directory of at least one        recipient to at least one server,    -   disconnecting the connection to at least one server,    -   at least one server relays the message to at least one recipient        terminal via telephony network or the Internet.

A video- and/or voicemail messaging method, comprising at least onesubscriber terminal and at least one server, in accordance with theinvention is characterised by the steps of,

-   -   choosing at least one message recipient or a group,    -   forming a communications connection to at least one server,    -   recording at least one voice/video message to at least one        server via at least one established communications connection,

transferring at least one contact directory of at least one recipient toat least one server,

-   -   disconnecting the connection to at least one server,    -   transferring at least one said message and at least one said        contact directory to a Store and Forward Server Network (SFSN),    -   at least one server in the SFSN or the original server relays at        least one message to at least one recipient terminal device        through the Internet or the telephony network,

A video- and/or voicemail messaging server, comprising at least onemedia player and/or a DSP and at least one data storage means andcommunications connections in and out of the telephony network, SFSNand/or the Internet in accordance with the invention is characterised inthat,

-   -   a recording is arranged to be made to the media player and/or        DSP through an established communications connection from a        subscriber terminal,    -   a capture of recipient contact information and/or other message        attributes from the subscriber terminal is arranged on the        server, and the contact information is arranged to be stored to        the storage means,    -   at least one media player and/or DSP is arranged to store the        recording to a data file,    -   at least one data file is arranged to be stored on the data        storage means,    -   at least one data file, or at least one copy of the data file is        arranged to be sent to another server in the SFSN and/or a        connection is arranged to be formed to at least one recipient.

A video- and/or voicemail messaging subscriber terminal in accordancewith the invention is characterised in that,

-   -   the user is arranged with the possibility to select at least one        recipient,    -   at least one communications connection is arranged to be formed        to the sewer upon selection of at least one recipient,    -   the recipient contact information is arranged to be sent to the        server,    -   the terminal is arranged to relay at least one video and/or        audio signal to the server,    -   the communication connection is arranged to be disconnected upon        a dedicated action or upon the fulfilment of dedicated criteria.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following the invention will be described in greater detail withreference to exemplary embodiments in accordance with the accompanyingdrawings, in which FIG. 1 demonstrates the principal method 10 of theinvention as a flow diagram. FIG. 2 demonstrates a more scalablemessaging method 20 in accordance with the invention. FIG. 3demonstrates a method applicable to circuit switched networks inaccordance with the invention. FIG. 4 demonstrates a subscriber terminal40 in accordance with the invention. FIG. 5 demonstrates a networkserver 50 in accordance with the invention. FIG. 6 demonstrates ascalable messaging architecture 60 in accordance with the invention.FIG. 7 displays typical screenshots of an exemplary embodiment of theinvention.

DETAILED DESCRIPTION OF EMBODIMENTS

In phase 110 of FIG. 1 the message recipient is chosen. The recipientmay be chosen by labeling the recipient with a pointer from the“contacts” file of the terminal device, the recipient may be chosen byspeech recognition, a dedicated keyboard accelerator, hot key, dedicatedkey or any combinations or permutations of these in some embodiments.Several recipients or a group may also be selected in some embodiments.A simple press of a button may also be used to select at least onerecipient. The terminal device is typically a computer, palmtop, laptop,or a mobile station, mobile phone, pager or any wired or wirelessinformation device. In some embodiments the terminal features Windows-,Windows NT-, Epoc-, Windows CE-, Unix-, Linux-, OS/2, Symbian, Epoc,PalmOS, Pocket PC, GEOS, MS-Stinger and/or Sybase or the like operatingsystem or software.

In phase 120 a packet switched or a circuit switched connection isestablished to the server. In some embodiments the subscriber terminalintercepts a selected recipient(s) contact directory, and forms acommunications connection to the server. The connection is typically aSS7-, GSM-, H323-, HTTP-, GSM-data, IP-RAN-, UMTS-, WAP-, Teldesic-,Inmarsat-, Iridium-, GPRS-, CDMA-data-, WCDMA-data, HTTP-, H323-, SMS-,MMS-, email-LAN-, TCP/IP-, imode-, Globalstar- and/or WLAN-connection insome embodiments.

In phase 130 the recipient contact information of at least one recipientor a recipient group is transferred to the server via the connection orotherwise. The recipient contact information may comprise the telephonenumber, static or dynamic IP-address, ISDN-number, MSISDN-number, email,SIP (Session Initiation Protocol) ID of the recipient, or any otherdirectory information. The subscriber terminal may translate directoryinformation from one type to the next depending on the requirements. Forexample, when the network is packet switched, a telephone number may beconverted to an IP-address in some embodiments. In some embodiments thedirectory information of the sender, such as Caller ID, telephonenumber, IP address or the like is transferred to the server as well. Thedirectory information of the recipients, sender or other messageattributes are transferred via the established communications channel,or through a separate communications or messaging channel. For example,if the connection is a phone call, DTMF tones, SMS messages, USSDmessages or the like may be used to communicate the said information. Ifthe connection is an IP connection, usually this same connection is usedto convey the said information.

In phase 140 the voice/video message is recorded in packet switched orcircuit switched format, but other formats are also possible in someembodiments. Consequently, the recording is written to a data file. Thedata file is typically an MP3-, WAV- or RealSystem Secure data file insome preferable embodiments. In some alternative embodiments the messagemay be recorded on tape. In some embodiments phase 140 may be executedprior to 130, or both may be executed concurrently.

In phase 150 the connection is disconnected. The connection ispreferably disconnected when the message has been completed. Theconnection may be disconnected by the user by a dedication action, suchas pressing a button or a like action. The fulfilment of a predefinedtime limit may disconnect the connection, as well as Voice ActivityDetection. If the user is silent, then either the terminal may concludethe message is completed, and disconnect the connection. Also therelease or press of a button may be used to disconnect the connection.

In phase 160 the server relays the message to the recipient(s) throughthe Internet or the telephony network. If the recipient terminal iscapable of receiving the data file, which means typically having apacket switched access to the recipient device, the message may be sentwith an packet switched connection, like IP, through the Internet, orthrough some other closed network. If the receiving terminal is acircuit switched device, for instance a telephone of any kind, theserver may call the number and once answered by a recipient or avoicemail box plays the message as playback down the phone line. In someembodiments of the invention, a special prefix and postfix may be storedto the server, which in some embodiments are associated and recognizedon the basis of the sender's directory information, the SIM or themobile station memory, and is played prior to the recording in the datafile or after it. The prefix and/or postfix could play for instance: “Inthe following you will hear a message from Ms. Vilma Väänänen.” MESSAGE“This completed the message of Vilma Väänänen.” In some preferableembodiments the sender is displayed on the recipient terminal screen.

When the recipient receives the message in phase 170, some indication ofthis is typically captured. The recipient is asked in the postfixwhether he would like to hear the message again, whether he understoodthe message, whether he is the person the message was intended to or anyother attributes related to the status of the message may be queried.The user may indicate his preferences by pressing e.g. a dedicatedbutton. This dedicated action will signal the server on the status of acertain message with respect to a certain recipient.

If the recipient is unavailable, the message may be stored on the serverfor some time, and attempts to deliver the message may be taken attimely intervals. In some embodiments the message is rerouted to analternative directory, such as email or voicemail box if the user isunavailable. The server may send a notification to the sender concerningwhich messages got delivered, which did not, how long will the messagesremain in the network and other related important delivery statusinformation relating to the delivery of said messages or attributedgiven by the recipient(s).

In phase 180 the recipient may answer sender directly. This may be doneby pressing a button after the data file has been played and dictatinganother data file or another dictation to tape, which will be sent tothe initial sender as a reply. The reply may be delivered in accordancewith the inventive methods 10, 20 and/or 30 in some embodiments. In somefurther embodiments it is also possible to forward messages to otherrecipients or third parties. The data file is typically an MP3-, WAV- orRealSystem Secure data file.

FIG. 2 displays a more scalable messaging method in accordance with theinvention. In phase 210 of FIG. 2 at least one recipient is chosen. Inphase 220 the subscriber terminal forms a connection to the server.Recipient contact information is typically transferred in phase 230, andthe recording of the said video/audio message is done in phase 240. Theconnection is disconnected in phase 250.

Before phase 260 the server establishes, whether it should deliver themessage to the recipient directly as in phase 160 of method 10, orforward it to other servers in a Store and Forward Server Networkassociated with the original server. In a sealable network architecture,phase 260 is typically proceeded with and both the recipient contactinformation and the message are passed onto the SFSN. In someembodiments where several recipients or at least one group exists, themessage may be relayed to some recipients by the original server and tosome by the SFSN. The SFSN is typically a network of servers linkedtogether through the Internet, telephony network, a Virtual PrivateNetwork (VPN), or some other communications or signalling network. Theconnections in the SFSN may be TCP/IP-, IP-, UDP-, HTTP, H323-, and/orFTC- in some embodiments.

In phase 270 the servers in the SFSN typically deliver a copy of themessage to a server near a recipient, and this server attempts to relaythe message to the said recipient. The server may attempt to form apacket switched connection to one, some or all of the recipientsterminals, attempt to dial a circuit switched telephone connection andplay the message as playback down the phone line, or email the messageto the recipient. In phase 280 the messages that were undelivered arestored on the SFSN.

In phase 290 some or all of messages that were undelivered in phase 270are being resent. The server may attempt to resend the message to thesame directories or addresses, or it may attempt to reroute the messageto an alternative address of the recipient. In some preferableembodiments the server sends a different message, for instance an SMSmessage, signifying that the message was not delivered and is on theserver for later retrieval. The notification message may contain accesscodes, directory information of the server, such as dial in phonenumber, URL address, IP address or the like.

In one alternative embodiment, the software in the subscriber terminalhas the telephone number of the software stored. Both the telephonenumber and the current IP-address are given to the server. Telephonenumbers and IP-addresses can then be used interchangeably when contactis made between software applications. This results to the effect thatinformation in packet switched format can be readily transmitted totelephone numbers, provided these telephone numbers have a correspondingIP-address.

In FIG. 3 the method 30 shows an inventive audio/video messaging methodwhich is most applicable to circuit switched communications, i.e.cellular e.g. GSM or CDMA or fixed line e.g. POTS (Pain Old TelephoneService). In phase 310 at least one recipient or a group are selectedfrom the telephone or mobile station memory. The recipient may be chosenby labeling the recipient with a pointer from the “contacts” file of theterminal device, the recipient may be chosen by speech recognition, adedicated keyboard accelerator, hot key, dedicated key or anycombinations or permutations of these in some embodiments. Severalrecipients or a group may also be selected in some embodiments. A simplepress of a button may also be used to select at least one recipient.

In some preferable embodiments the mobile station features SIMApplication Toolkit (SAT), Java Virtual Machine or Wireless TelephonyApplication Interface support WTAI. A special menu e.g. “VoiceMessages”, or “Instant Voice Messages” or “Uni-directional phone call”menu may be realised in accordance with the invention. The recipient maybe selected from this menu, typically on the SIM and/or mobile stationmemory with the aforementioned methods.

In phase 320 the terminal intercepts the selected recipient telephonenumber, and dials a telephone number associated with the server.

Once the connection to the server is operational, either the terminalsends or server retrieves the recipient(s) contact directory and thetelephone number of the sender or caller ID of the message in phase 330.These telephone numbers may be sent through SS-, USSD-, SMS- orSS7-channels, or as DTMF tones through the connection. The server thenrecords these numbers and translated or modifies them according to somerules or definitions to enable further delivery of the message. Once therelevant information has been signalled between the terminal and theserver, either one may indicate to the user that the dictation maybegin.

In phase 340 the message is being dictated through the connection andrecorded on the server. Consequently, the recording is written to a datafile. The data file is typically an MP3-, WAV- or RealSystem Secure,u-law, A-law, PCM or ADPCM data file in some preferable embodiments. Insome alternative embodiments the message may be recorded on tape. Insome embodiments the process is cancelled if the connection breaks andan error notification indicating this may be sent by SMS.

In phase 350 the dial up connection is disconnected. The connection ispreferably disconnected when the message has been completed. Theconnection may be disconnected by the user by a dedicated action, suchas pressing a button or a like action. The fulfilment of a predefinedtime limit may disconnect the connection, as well as Voice ActivityDetection. If the user is silent, then either the terminal may concludethe message completed, and disconnect the connection. Also the releaseor press of a button may be used to disconnect the connection.

In phase 360 the server examines the message delivery requests. If it isdeterminable that the recipient is near the server, from the telephonenumber, country or area code, VLR (Visitor Location Register), HLR (HomeLocation Register) or any other source, the server may proceed to phase371. If the server concludes that reaching the recipient is not feasibleor justified according to set criteria, it will proceed to phase 370.Other logical reasons apart from narity, for example cost of terminatingconnection may determine whether to proceed to 370 or 371, or neither.In extreme circumstances, if the delivery of the message is impossible,the server may delete the message and send a notification to therecipient, for example by SMS or email.

Assume the server proceeded to 371. In this phase the original servercalls the numbers of the recipients and once answered by a recipient ora voicemail box plays the message as playback down the phone line. Insome embodiments of the invention, a special prefix and postfix may bestored to the server, which in some embodiments are associated andrecognized on the basis of the sender's directory information, the SIMor the mobile station memory, and is played prior to the recording inthe data file or after it. The prefix and/or postfix could play forinstance: “In the following you will hear a message from Ms VilmaVäänänen.” MESSAGE “This completed the message of Vilma Väänänen.” Insome preferable embodiments the sender is displayed on the recipientterminal screen. In some embodiments, the caller ID, the name of thesender or the like is displayed by the Caller ID property of thenetwork, or by a SMS, OTA (Over the Air) or WAP-flash, or SMS broadcastmessage.

In phase 381 the undelivered messages are stored at the server or in theSFSN. In phase 391 the original server or the SFSN attempts to deliverthe message at timely intervals, for example by placing further calls.In some embodiments the message is rerouted to an alternative directory,such as email or voicemail box, or the like if the user is unavailable.Alternatively, the messages could be attempted to send via a packetswitched connection as described in FI20001838 of the applicant. Theserver may send a notification to the sender concerning which messagesgot delivered, which did not, what was the reason; was the recipientbusy, refused the call, in radio shadow, how long will the messagesremain in the network and other related important delivery statusinformation relating to the delivery of said messages. In somepreferable embodiments the server sends a different message to therecipient, for instance an SMS message, signifying that the message wasnot delivered and is held on the server for later retrieval. Thenotification message may contain access codes, directory information ofthe server, such as dial in phone number, URL address, IP address or thelike.

Assume the server proceeded to phase 370. Here the SFSN servers relaythe message to the recipients through the Internet or the Telephonynetwork. The call to the recipient is sometimes made from an optimalserver in the SFSN. This may be the closest server or the one with themost inexpensive communications connection to the recipient. The choiceof the server making contact with a particular recipient is determinedby delivery criteria set in the network. When the same message isdelivered to various recipients in different locations, copies of thesame message may be routed to several different servers, from which thecall is made. The message delivery process may be as described in phase371.

In phase 380, the undelivered messages are stored on the SFSN. Themessages may be stored for a period of time, before proceeding to phase390. In some alternative embodiments there is an iteration loop betweenphases 380 and 390. In some cases several attempts to call a recipientare made, and a notification or rerouting of the message are taken aftersome attempts have failed. Any SFSN server may send a notification tothe sender concerning which messages got delivered, which did not, howlong will the messages remain in the network and other related importantdelivery status information relating to the delivery of said messages.

The recipients may also answer sender directly, upon reception of amessage. This may be done by pressing a button after the data file hasbeen played and dictating another data file or another dictation totape, which will be sent to the initial sender as a reply. The reply maybe delivered in accordance with the inventive methods 10, 20 and/or 30in some embodiments. In some further embodiments it is also possible toforward messages to other recipients or third parties. The data file istypically an MP3-, WAV- or RealSystem Secure, u-law, A-law, PCM or ADPCMdata file.

During, in between or after any of the phases of methods 10, 20, 30,directory lookup may be executed in some preferable embodiments. Thetelephone number of the recipient is converted to an IP-address in onepreferable embodiment. A prior art solution to directory lookup andconversion is presented in my patent application “Telenetwork directorytemplate”, FI19992774, which is taken here as reference. Directorylookup is here established as the interchange retrieval and/orcomparison of any directory information such as email-, IP-address, URL,ISDN number, MSISDN, phone number or the like to another correspondingemail-, IP-address, URL, ISDN number, phone number or the like directoryfrom the network, network server and/or terminal in order to deliver themessage to a directory. Especially in cases where the IP-address of therecipient is a dynamic one, the directory lookup is an advantageousfeature. In some embodiments where the recipient has a static IPaddress, the IP-address need not be looked up separately every time. Insome preferable embodiments IP-addresses of recipients are stored on thesubscriber terminal. In some embodiments only static IP-addresses ofrecipients are stored.

During, in between or after any of the phases of methods 10, 20, 30,signal barring may be executed in some preferable embodiments. In someembodiments the recipients may decline to receive messages from unwantedparties, for example by setting conditions to their subscriber terminal.

Voice recognition may be employed during, before, in between or afterany of the phases of methods 10, 20, 30. In some preferable embodiments,voice recognition is used to convert the dictation into a written email,SMS-, MMS-message or the like.

In some embodiments, at least one subscriber terminal and at least oneserver form a Virtual Private Network (VPN).

A Regret function or request may be employed during, before, in betweenor after any of the phases of methods 10, 20, 30 in order to destroy anunwanted intermittent or complete message. It may be sent to the serverdirectly, which will handle the message cancellation on itself or theSFSN, even when it has already been sent. In some embodiments themessage is destroyed upon receipt of the regret message on any server,in some embodiments after the receiver has played the message or in someembodiments irrespective of this.

In some embodiments, it is possible to utilize Autoplay upon reception.In this embodiment, the audio/video message is played automatically uponreception of the message. Typically, this means opening the filecontaining the message, and possibly employing decoding and/ordecryption methods in some embodiments. In some embodiments where themessage arrives by playback down the phone line, Autoplay is used toautomatically answer these phone calls and play the call to thespeaker(s) of the terminal. In this embodiment the server typically hasto send some indication, signifying to the recipient terminal that it isindeed this message and not any call, in which case Auto answer may beemployed.

Charging and/or billing of the message may be realised during before, inbetween or after any of the phases of methods 10, 20, 30. In somepreferable embodiments, the message is billed with a fixed price and hasa maximum duration. This way the service provider may estimate the realcost of a message very accurately and charge a premium for the service.This could be realised with a toll free number that has a fixedconnection charge for instance. It is also possible to bill the useronly after the message has been successfully delivered and notified.This could be realised for example by having everything else free, andcharging for the last SMS notification. Alternatively it is possiblejust to bill the user based on the telephone or Internet connection, forexample on a cost per connection minute or on a cost per transmitted orreceived bit.

The subscriber terminal is typically a mobile station equipped with anInternet connection and/or a telephony network connection. The mobilestation typically abides to UMTS-, GSM-, WAP-, Teldesic-, Inmarsat-,Iridium-, GPRS-, CDMA-, HTTP-, H323-, SMS-, MMS-, and/or WCDMA-standardsin some preferable embodiments. The subscriber terminal used in themethod may also be a PC, PDA, Palm Computer or an Apple Macintoshcomputer equipped with an Internet connection and/or a telephony networkconnection in some preferable embodiments. The subscriber terminal inaccordance with the invention has typically an operating system likeWindows-, Windows NT-, Epoc-, Windows CE-, Unix-, Linux-, OS/2, Symbian,Epoc, PalmOS, Pocket PC, GEOS, Ms-Stinger and/or Sybase. The executionof methods 10, 20, 30 is typically realised with a separate softwareapplication operating under the control of those operating systems.Alternatively, the execution of methods 10, 20, 30 may be realised withsoftware that is integrated to any of the above operating systems. Insome embodiments the execution of methods 10, 20, 30 and theirfavourable permutations and further embodiments may be realised by OEMsoftware for mobile stations, modems, computers, radio, SIM cards and/orline cards. In some embodiments the execution of methods 10, 20, 30 maybe realised with software that is integrated to any email clientsoftware, such as Microsoft Outlook, Outlook Express or the like. Insome embodiments the execution of methods 10, 20, 30 may be realisedwith software that is developed using SAT (SIM Application Toolkit) orWTAI (Wireless Telephony Application Interface) of WAP (WirelessApplication Protocol).

Any sent or received messages or their drafts may be saved, forwardedand replied to during, before, in between or after any of the phases ofmethods 10, 20, 30 on the network servers, on the SFSN or on theterminals or to the voicemail box, email or the like of the party inquestion.

The communications connections used between the terminals and theservers or in the SFSN are typically compliant with SS7-, GSM-, H323-,HTTP-, GSM-data, IP-RAN-, UMTS-, WAP-, Teldesic-, Inmarsat-, Iridium-,GPRS-, CDMA-data-, WCDMA-data-, HTTP-, H323-, SMS-, MMS-, USSD-,email-LAN-, TCP/IP-, UDP, imode-, Globalstar- and/or WLAN-connections insome embodiments.

The server typically features several incoming sockets for incomingpacket switched connections and incoming dial in ports for incomingtelephone calls, and features also the outgoing ports and sockets forboth connections. In addition the server typically features also a mediaplayer and a media recorder both of which may be integrated in someembodiments, alternatively tape recording and/or reproduction may alsobe used. The server typically also comprises a database and a databasemanagement system (DBMS). The recorded media files are stored in thedatabase. The DBMS or any other associated data management logic thendirects the files to the media player, provided the server decides torelay the message to the recipient directly, or the DBMS transfers thefiles to other servers in the SFSN, so that another server in the SFSNmay deliver it to a recipient. The database can be any database or datamanagement utility, for example Oracle, Solid, TimesTen, Clustra,Informix, Sybase, IBM D2, or any other database or data managementsystem.

FIG. 4 shows an exemplary embodiment of a subscriber terminal inaccordance with the invention. In FIG. 4 the user interface 400 of apreferable subscriber terminal is illustrated. The user interface 400 istypically a PDA and/or a mobile stations front- or backend, or a virtualtelephone on a PC screen. In one preferable embodiment, once the VSMS,or any other button or a combination of buttons is pressed, a recordingis begun, and the message may be transmitted in accordance with theinventive methods 10, 20 and/or 30. The release of the VSMS button, orany other button or their combination may finish the recording and sendthe message in accordance with the invention. In some embodiments thebuttons may be pressed physically or with a mouse pointer from a screen.In some embodiments separate dedicated keys, combinations of keys,shortcut keys, keyboard accelerators or the like are used to record anddeliver messages. In some embodiments, dedicated keys, combinations ofkeys, shortcut keys, voice recognition keyboard accelerators or the likeare used to record and deliver messages specifically to recipients towhom the dedicated keys, combinations of keys, shortcut keys, vocalsound, keyboard accelerators are dedicated to. For example, in oneembodiment the button “9” or Ctrl+M could be used to record and deliverthe message e.g. to the “M”other of the sender, i.e. mother of thesender. Naturally any other logical relationship between the hot key andthe recipient is possible.

In one embodiment the arrival of the message, or a packet streamcontaining the message may be indicated on the screen 410, or byflashing a light on the VSMS button or any other button or theircombination. Once the recipient holds the button down the message isplayed from the audio devices of the subscriber terminal. In somepreferable embodiments the inventive subscriber terminal features alsoan inbox for arrived messages.

In one embodiment the user interface 400 is the user interface of amobile station. In one embodiment the method is realized with a computerprogram that is arranged to run on the SIM card (Subscriber IdentityModule) of the mobile station. The SIM card typically bas a CPU,EEPROM-, ROM- and RAM memories. In one phase of this special embodimentthe message recipient, several recipients or a group may be chosen fromthe memory of the SIM card or from the memory of the mobile station, orit is inputted to the mobile station. When a dedicated action, such aspressing a button, is taken, a telephone connection is formed to amessaging server. Then the Caller ID and the telephone numbers of therecipients are transmitted to the messaging server with DTMF tones, SMS,USSD, ISDN d-channel signalling or like signalling. Following this adata file is recorded from the dictation, voice or video that isavailable through the connection to messaging server. A mediaplayer/recorder and/or DSP is typically located on the server and islistening to the telephone connection. After this the message servertransfers the file to the recipient, to a secondary address of therecipient or dials the telephone number of the recipient and plays themessage as playback to the recipient when the call is answered or to thevoicemail box if the call is answered by the voicemail box.Alternatively the server may store the message with the addressinformation in a DBMS or database. The message can then be later sent toat least one recipient. This alternative embodiment is especiallysuitable when there are separate incoming and outgoing connections.Likewise the file can be transferred to a SFSN, which delivers themessage. The dialling of a data or a voice call and transmittance ofother information is realised in the terminal 400 using the proactiveSIM feature of the SAT SIM Application Toolkit, which is specified inthe phase 2+ of the GSM specification in some embodiments.

In some embodiments of the invention, a special prefix and postfix maybe stored on the network messaging server, the SIM or the mobile stationmemory, is played prior and after the recording in the data file to therecipient, respectively. The prefix and/or postfix can be provided bythe messaging server, or they can be recorded to the messaging server bythe user from the mobile station. The prefix and/or postfix could playfor instance: “In the following you will hear a message from Mr. JeroJävenpää” MESSAGE “This completed the message of Jero Jävenpää.” Thefact that the message was received could be detected in various ways inaccordance with the invention. When the recipient or the voicemail boxanswers or hangs up, a DTMF tone or a USSD signal may be transmitted bythe recipient and detected by the server or the network which may beused to notify the sender or the network that the message was delivered,e.g. with an SMS message of a flash message on the screen. Alternativelythe recipient could be asked to press a button or perform a dedicatedaction in order to signal that the message was indeed received and/orunderstood. If one or some of the recipients are unavailable, themessage may be kept in memory and several other attempts to send themessage may be taken. In some embodiments it is possible to setexpiration conditions for the message, such as time, demands on memoryby other functions, or various other conditions. In some embodiments theSIM, the mobile station, and the messaging server may execute themethods 10, 20, 30 or any permutation of these together, by for examplethe SIM performing the recipient selection and commands for forming ordialling connection, and the network server by providing a media player.

FIG. 5 exhibits a schematic exemplary embodiment of the messaging serverin accordance with the invention. The dial in ports and/or in sockets510 take the incoming phone calls or other incoming circuit switched orpacket switched connections. The media recorder 520 is arranged torecord the audio and/or video that comes in through the connections tothe ports and sockets 510. The recorder 520 records and digitises theinput to a data file, which is typically of MP3-, WAV- or RealSystemSecure, but can be any file format. In alternative embodiments a DSPcircuit is interfaced with the media player and the database 530, andthis DSP circuit is used to digitise the transmissions and store them todata files. The data file is stored to the database 530. The databasecan be any database or data management utility, for example Oracle,Solid, TimesTen, Clustra, Informix, Sybase, IBM D2, or any otherdatabase or data management system. The database 530 and associatedapplication and management logic analyse the data file and itsassociated attributes and transfer the file to either a further serverin the SFSN, or to the media player 540. For example if a recipient hasa foreign country code, the server may relay the file to a SFSN serverin that country or near to it. If the recipient is analysed to be in thedomain of the server 500, the server uses the dial out ports or outsockets 550 to form a connection to the recipient. When a connection isestablished, the media player 540 is used to play the message throughthe connection to the recipient, along with any pre- and/or postfixesassigned by the DBMS or application logic.

In some embodiments the media player 540 and 530 may be integrated. Itis clear that both are capable of processing several requests inparallel depending on how many processing requests the server is engagedin.

Low latency is a preferable characteristic of the dial in ports or insockets. Due to this the server 500 is typically a low latency server,associated closely with network elements. In some preferable embodimentsthe server is associated with an MSC, BSS, any switching centre or anycellular or fixed telephony network element. In some embodiments theserver is persistently distributed over the network that it covers.

FIG. 6 shows schematic miniature network topology in accordance with theinvention. The subscriber terminals 650, 651 are in the domain of theserver 610, and the terminals 652, 653 are in the domain of server 620.The servers 610 and 620 form a miniature Store and Forward ServerNetwork. Consider a case where a message is placed from the terminal 650to terminals 652 and 651. In some embodiments the terminal 650 forms aconnection to server 610, and the message is recorded to the saidserver. Server 610 iterates alternatives to deliver the message to bothrecipients. In some embodiments, it will form a connection to terminal651 by itself and play the message if the recipient is available.Meanwhile in some embodiments, the server 610 relays a copy of therecorded file to the other server 620 in the SFSN. The file can berelayed by FTP (File Transfer Protocol) or by a traction betweendatabases or by any other data management method. The server 620 thencalls the recipient 652 and plays the data file, if the recipient isavailable.

The subscriber terminals 650, 651, 652, 653 may be any fixed line orwireless device with a telephony or Internet connection. In someembodiments the subscriber terminal is typically a mobile stationequipped with an Internet connection and/or a telephony networkconnection. The mobile station typically abides to UMTS-, GSM-, WAP-,Teldesic-, Inmarsat-, Iridium-, GPRS, CDMA-, HTTP-, H323-, SMS-, MMS-,and/or WCDMA-standards in some preferable embodiments. The subscriberterminal used in the method may also be a PC, PDA Palm Computer or anApple Macintosh computer equipped with an Internet connection and/or atelephony network connection in some preferable embodiments. Thesubscriber terminal in accordance with the invention has typically anoperating system like Windows-, Windows NT-, Epoc-, Windows CE-, Unix-,Linux-, OS/2, Symbian, Epoc, PalmOS, Pocket PC, GEOS, Ms-Stinger and/orSybase. The execution of methods 10, 20, 30 is typically realised with aseparate software application operating under the control of theseoperating systems. Alternatively, the execution of methods 10, 20, 30may be realised with software that is integrated to any of the aboveoperating systems. In some embodiments the execution of methods 10, 20,30 and their favourable permutations and further embodiments may berealised by OEM software for mobile stations, modems, computers, radio,SIM cards and/or line cards. In some embodiments the execution ofmethods 10, 20, 30 may be realised with software that is integrated toany email client software, such as Microsoft Outlook, Outlook Express orthe like. In some embodiments the execution of methods 10, 20, 30 may berealised with software that is developed using SAT (SIM ApplicationToolkit) or WTAI (Wireless Telephony Application Interface) of WAP(Wireless Application Protocol).

The servers 610, 620 are typically as described in FIG. 2, except thatthey may have a separate SFSN data connection between their databasesand application logic. In embodiments where some subscribers arewireless, the servers 610, 620, or the SFSN in general may exhibithandover functions. When a subscriber terminal 650 enters the area wherethe latency or cost of connection for the server 620 is smaller, it ispreferable that it should contact 620 instead. To facilitate thesehandovers servers 610, 620 may be assigned to different subscribers 650,651, 652, 653 dynamically during roaming, or later by informationderived from the HLR, VLR or any cellular network element that containsthe location of the subscriber. The requests for handover may beinitiated by the network, the mobile station or both.

The servers 610, 620, and the subscriber terminals 650, 651, 652, 653may feature transcoders, which may modify the message format from one tothe next. For example a message left with a normal phone call could betranscoded into an MMS message. Transcoding between any communicationprotocols, such as SS7-, GSM-, H323-, HTTP-, GSM-data, IP-RAN-, UMTS-,WAP-, Teldesic, Inmarsat-, Iridium-, GPRS-, CDMA-data-, WCDMA-data-,HTTP-, H323-, SMS, MMS-, USSD-, email-LAN-, TCP/IP-, UDP-, POTS-, NDC-,PDC-, imode-, Globalstar- and/or WLAN-, or file formats, such as MP3,WAV, RealSystem Secure or the like is in accordance with the invention.

FIG. 7 displays typical screenshots of an exemplary embodiment of theinvention where the subscriber terminal is a mobile station, typically aGSM-CDMA- and/or a WAP mobile station. The main menu item 710 displays“Voice Messages”, and is in the main menu of SIM or mobile stationoperating system software in some embodiments. The main menu item 710could bear any name e.g. “Instant Voice Message” in accordance with theinvention. By choosing 711 “send” the user is directed to the names andtelephone numbers directory of the mobile station, which may be storedon the SIM, mobile station memory or network. Once in the directory theuser may send a voice message to a recipient, several recipients or agroup of recipients by selecting the recipients from the names directorywith a dedicated action. Alternatively the user may enter at least onetelephone number or other contact directory directly to the mobilestation at any stage.

By choosing 712 “options” the user is directed to the Options menu 720.In this menu, the user may record prefixes and postfixes, or alter Sendoptions or Receive options. Send options and receive options may featuresaving messages at any stage of methods 10, 20 and/or 30, or preferencesconcerning alternative routings to alternative directories, such asemail addresses, IP addresses or the like.

The inventive method and arrangement 70 is typically realised with WTAIor SIM Application Toolkit (SAT) in some embodiments.

It is possible to exchange methods or means, any parts of the invention,duplicates of the invention, entities composed of the invention orinventive idea to any party in exchange for economic benefit, otherbenefit, or for no benefit at all.

The invention has been explained above with reference to theaforementioned embodiments and several commercial and industrialadvantages have been demonstrated. The inventive methods and means understudy allow faster voice messaging and enable similar, but not identicalaudio/video message “ping ball” as described in the priority document.The sending of voicemail in accordance with the invention isinstantaneous and involves no different telephone numbers for the senderto remember. The reception of messages is always instantaneous, providedthe recipient is available, and only if not available, may the deliveryof the messages be delayed.

The invention has been explained above with reference to theaforementioned embodiments. However, it is clear that the invention isnot only restricted to these embodiments, but comprises all possibleembodiments within the spirit and scope of the inventive thought and thefollowing patent claims.

1. A mobile video- and/or voicemail messaging method, comprising atleast one mobile subscriber terminal and at least one server, saidmethod comprising the steps of: choosing at least one message recipientor a group at a mobile subscriber terminal; forming at least one packetswitched wireless communications connection between said mobilesubscriber terminal and at least one server; transferring at least onecontact directory of at least one recipient to said at least one servervia said packet switched wireless connection; recording at least onevoice/video message to at least one data file on said at least oneserver via said at least one packet switched wireless communicationsconnection; disconnecting said packet switched wireless connection tosaid at least one server; and said at least one server relaying the datafile message to at least one recipient terminal via telephony network orthe Internet.
 2. A mobile video- and/or voicemail messaging method,comprising at least one mobile subscriber terminal and at least oneserver, said method comprising the steps of: choosing at least onemessage recipient or a group; forming at least one packet switchedwireless communications connection between a mobile subscriber terminaland a server; transferring at least one contact directory of at leastone recipient to said server via said at least one packet switchedwireless connection; recording at least one voice/video message to atleast one data file on said server via said at least one packet switchedwireless communications connection; disconnecting the packet switchedwireless connection to said server; transferring at least one said datafile message and at least one said contact directory to a Store andForward Server Network (SFSN); and at least one server in the SFSN orsaid server relaying said at least one data file message to at least onerecipient terminal device through the Internet or a telephony network.3. The method as claimed in claim 1, wherein undelivered messages arestored at the SFSN or the server, and attempts to resend said at leastone data file message to said at least one recipient are made, and/orattempts to resend to alternative contact directories of said at leastone recipient are made.
 4. The method as claimed in claim 1, whereinundelivered messages are stored at the SFSN or the server for a giventime, after which they are deleted.
 5. The method as claimed in claim 1,wherein said recipient contact directory may be a telephone number, ISDNnumber, URL-address, email, IP-address, and the recipient contactinformation is readily and transparently converted from one directory tothe next in accordance with message delivery requirements.
 6. The methodas claimed in claim 1, wherein charging and/or billing for the messagedelivery may be realized during, before, in between or after any of thesteps, and may be fixed price, cost per connection minute or cost pertransmitted bit based.
 7. The method as claimed in claim 1, whereinduring, before, in between or after any of the steps, at least one ofthe sender and said at least one recipient may reply, save and/orforward messages on the network, the server and/or a subscriberterminal.
 8. The method as claimed in claim 1, wherein communicationsconnections used between said at least one terminal and said at leastone server or in the SFSN are dial connections, data connections orpacket switched connections, compliant with: SS7-, GSM-, H323-, HTTP-,GSM-data, IP-RAN-, UMTS-, WAP-, Teldesic-, Inmarsat-, Iridium-, GPRS-,CDMA-data-, WCDMA-data-, SMS-, MMS-, USSD-, email-LAN-, TCP/IP-, UDP-,POTS-, NDC-, PDC-, imode-, Globalstar- and/or WLAN-connections.
 9. Themethod as claimed in claim 1, wherein at least one subscriber terminaland at least one server form a Virtual Private Network (VPN).
 10. Avideo- and/or voicemail messaging server, comprising: at least one mediaplayer and/or a DSP and at least one data storage means andcommunications connections in and out of a telephony network, SFSNand/or the Internet, wherein a recording is arranged to be made to atleast one of the media player and DSP through an established packetswitched communications connection from a mobile subscriber terminal; acapture of recipient contact information and/or other message attributesfrom the mobile subscriber terminal is arranged wirelessly via saidpacket switched connection on a server, and the contact information isarranged to be stored to the storage means; at least one media playerand/or DSP is arranged to store the recording to a data file; at leastone data file is arranged to be stored on the data storage means; atleast one data file, or at least one copy of the data file is arrangedto be sent to another server in the SFSN and/or a connection is arrangedto be formed to at least one recipient.
 11. The video- and/or voicemailmessaging server as claimed in claim 10, wherein said storage means is adatabase associated with a data management utility.
 12. A video- and/orvoicemail messaging mobile subscriber terminal, wherein a user of themobile subscriber terminal is arranged with the possibility to select atleast one recipient from the mobile subscriber terminal; at least onepacket switched wireless communications connection is arranged to beformed to a server upon selection of said at least one recipient;recipient contact information is arranged to be sent wirelessly via saidpacket switched wireless communications connection to the server; theterminal is arranged to relay at least one video and/or audio signal tothe server for recording to a data file via said at least one packetswitched wireless connection; and the packet switched wirelesscommunication connection is arranged to be disconnected upon a dedicatedaction or upon the fulfillment of dedicated criteria.
 13. The video-and/or voicemail messaging mobile subscriber terminal as claimed inclaim 12, wherein the mobile subscriber terminal is a PC, PDA-mobilestation and/or a Apple Macintosh computer with a wireless communicationconnection compliant with at least one of the following: SS7-, GSM-,H323-, HTTP-, GSM-data, IP-RAN-, UMTS-, WAP-, Teldesic-, Inmarsat-,Iridium-, GPRS-, CDMA-data, WCDMA-data, SMS-, MMS-, USSD-, email-LAN-,TCP/IP-, UDP-, POTS-, PDC-, NDC-, imode-, Globalstar- and/orWLAN-connections.
 14. The method as claimed in claim 2, whereinundelivered messages are stored at the SFSN or the server, and attemptsto resend at least one message to at least one recipient are made,and/or attempts to resend to alternative contact directories of at leastone recipient are made.
 15. The method as claimed in claim 2, whereinundelivered messages are stored at the SFSN or the server for a giventime, after which they are deleted.
 16. The method as claimed in claim2, wherein recipient contact directory may be a telephone number, ISDNnumber, URL-address, email, IP-address, and the recipient contactinformation is readily and transparently converted from one directory tothe next in accordance with message delivery requirements.
 17. Themethod as claimed in claim 2, wherein charging and/or billing for themessage delivery may be realized during, before, in between or after anyof the steps, and may be fixed price, cost per connection minute or costper transmitted bit based.
 18. The method as claimed in claim 2, whereinduring, before, in between or after any of the steps, the sender and/orat least one recipient may reply, save and/or forward messages on thenetwork, the said server and/or a subscriber terminal.
 19. The method asclaimed in claim 2, wherein communications connections used between atleast one terminal and at least one server or in the SFSN are dialconnections, data connections or packet switched connections, typicallycompliant with: SS7-, GSM-, H323, HTTP-, GSM-data, IP-RAN-, UMTS-, WAP-,Teldesic-, Inmarsat-, Iridium-, GPRS-, CDMA-data-, WCDMA-data-, SMS-,MMS-, USSD-, email-LAN-, TCP/IP-, UDP-, POTS-, NDC-, PDC-, imode-,Globalstar- and/or WLAN-connections.
 20. The method as claimed in claim2, wherein at least one subscriber terminal and at least one server forma Virtual Private Network (VPN).